Personal messaging security

ABSTRACT

A method may include creating, by a user device, an electronic message, the electronic message comprising destination information corresponding to an intended recipient of the electronic message. The method many include receiving, by the user device and from a user, a security key corresponding to a particular type of user input and corresponding to the intended recipient of the electronic message. The method may include encrypting, by the user device, the electronic message based on the security key, and the method may include communicating, by the user device, the electronic message based on the destination information corresponding to the intended recipient.

BACKGROUND

Electronic communications continue to be a more and more pervasivecomponent of modern society. Examples of such electronic communicationsinclude e-mail messages, text messages, instant messages, voicemails,video messages, and other types of personal communications. However,currently available technologies do not provide adequate solutions forensuring that electronic communications remain secure.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram of an example overview of an implementationdescribed herein;

FIG. 2 is a diagram of an example environment in which systems and/ormethods, described herein, may be implemented;

FIG. 3 is a diagram of an example user device;

FIG. 4 is a diagram of example components of a device according to oneor more implementations described herein;

FIG. 5 is a diagram of example functional components of a user deviceaccording to one or more implementations described herein;

FIG. 6 is a diagram of an example process for creating and communicatingan electronic message according to one or more implementations describedherein;

FIG. 7 is a diagram of an example process for decrypting an electronicmessage according to one or more implementations described herein;

FIG. 8 is a diagram of an example process for communicating anelectronic message according to one or more implementations describedherein; and

FIG. 9 is a diagram of an example process for communicating anelectronic message according to one or more implementations describedherein.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same labels and/or reference numbers in different drawings mayidentify the same or similar elements.

In one or more implementations, described herein, devices may be used toprovide enhanced security solutions for electronic messages.

FIG. 1 is a diagram of an example overview of an implementationdescribed herein. As depicted in FIG. 1, a user may operate a userdevice (e.g., a mobile telephone, a personal computer, etc.) to createan e-mail, a text message, or another type of electronic message. Priorto sending the electronic message to an intended recipient, the user mayimplement one or more security measures to ensure that the electronicmessage is not seen or accessed by an unintended recipient. For example,the user may create a personalized security key (also referred to hereinas “security key”) that may be used to encrypt the electronic message.The personalized security key may also be used by the intended recipientto decrypt the electronic message.

The personalized security key may be created by one or more of a varietyof user inputs. For instance, the personalized security key may becreated by a user moving or gyrating the user device in a particularpattern, the user speaking into a microphone of the user device, theuser typing a sequence of characters into a keyboard of the user device,etc. Additionally, or alternatively, the personalized security key maybe personalized in the sense that only the user sending the message andthe intended recipient would know, or could access, the personalizedsecurity key. For example, prior to the user sending the electronicmessage, the user and the intended recipient may have agreed thatelectronic communications between the user and the intended recipientwould be encrypted and decrypted by a personalized security key createdby gyrating a user device in a circular pattern.

In addition to the personalized security key, the user may impose timelimits for viewing the electronic communication. For example, the usermay specify that the personalized security key used to encrypt theelectronic message will only be valid for decrypting the electronicmessage for a particular period of time (e.g., the next thirty minutes).In such a scenario, even if the intended recipient knew or had access tothe personalized security key, the intended recipient may not be able toaccess the contents of the electronic message once the specified timeperiod for accessing the electronic message had expired.

Accordingly, an implementation, described herein, may provide multiplesolutions for enhancing the security of electronic messages. Forinstance, an implementation, described herein, may enable users toencrypt electronic messages using security keys that may correspond to aparticular type of user input (e.g., user device gyrations, audioinputs, etc.). Additionally, or alternatively, an implementation,described herein, may enable users to specify the actual content of thesecurity key (e.g., a particular gyration pattern, a particular phraseor word, etc.). In addition, an implementation, described herein, mayenable users to impose timing constraints on decrypting or viewing thecontents of an electronic message. As a result, even if an individual,other than the intended recipient, were to have physical possession ofthe intended recipient's user device, the individual would not be ableto obtain access to the contents of the electronic message.

FIG. 2 is a diagram of an example environment 200 in which systemsand/or methods, described herein, may be implemented. As depicted,environment 200 may include user devices 210-1, 210-2, 210-3, . . . ,210-N (where N≧1) (hereinafter referred to collectively as “user devices210,” and individually as “user device 210”), network 220, and messagesecurity system 230.

User device 210 may include one or more of a variety of devices capableof network communications. For example, user device 110 may include atelephone, a smart phone, a laptop computer, a tablet computer, adesktop computer, or another type of computing or communication device.User device 210 may be capable of operating in accordance with thesystems, devices, processes, operations, and technical environmentsdescribed herein. For instance, user device 210 may be capable ofcommunicating with other user devices 210, message security system 230,or other devices that may be associated with network 220.

For example, user device 210 may be capable of creating electronicmessages, associating the electronic messages with personalized securitykeys, imposing key durations on the electronic messages or thepersonalized security keys, and communicating the electronic messages toone or more other user devices 210. Additionally, or alternatively, userdevice 210 may be capable of receiving electronic messages, obtainingpersonalized security keys based on personalized security keyinformation (also referred to herein as “security key information”)received from a user, and use the personalized security keys to decodethe electronic messages. Additional, or alternative, features,operations, and/or characteristics that may correspond to user device210 are discussed throughout this description.

Network 220 may include any type of network or combination of networks.For example, network 220 may include a local area network (LAN) (e.g.,an Ethernet network), a wireless LAN (WLAN) (e.g., an IEEE 802.11network), a wide area network (WAN) (e.g., the Internet), or a wirelessWAN (WWAN) (e.g., a Long-Term Evolution (LTE) network, a High-SpeedPacket Access (HSPA) network, an Evolved High Rate Packet Data (eHRPD)network, etc.). Network 220 may also, or alternatively, include an IMSnetwork, a fiber optic (e.g., a fiber optic service (FiOS)) network, avoice over Internet Protocol (VoIP) network, a metropolitan area network(MAN), an ad hoc network, or a telephone network (e.g., a PublicSwitched Telephone Network (PSTN)). As such, depending on theimplementation, network 220 may provide one or more of a variety ofservices and/or technological capabilities with respect to user devices210 and message security system 230.

Message security system 230 may include one or more of a variety ofcomputing devices. For example, message security system 230 may includea server, a cluster of servers, or one or more other types of computingor communication devices. Additionally, or alternatively, messagesecurity system 230 may operate in one or more of a variety of networkcapacities (e.g., a database server, a file server, an e-mail server, anapplication server, etc.).

Additionally, or alternatively, message security system 230 mayparticipate in, enable, or facilitate electronic message security asdescribed herein. For example, message security system 230 may provideuser devices 210 with software for performing one or more of theoperations described herein. Message security system 230 may also, oralternatively, enable user devices 210 to register with message securitysystem 230 in order to send and/or receive secured electronic messagesas described herein. Additionally, or alternatively, message securitysystem 230 may provide a repository for electronic messages and/orpersonalized security keys as described herein.

While FIG. 2 shows a particular number and arrangement of devices, inpractice, environment 200 may include additional devices, fewer devices,different devices, or differently arranged devices than are shown inFIG. 2. Also, although certain connections are shown in FIG. 2, theseconnections are simply examples and additional or different connectionsmay exist in practice. Each of the connections may be a wired and/orwireless connection. Further, each device may be implemented asmultiple, possibly distributed, devices.

FIG. 3 is a diagram of an example user device 210. As illustrated inFIG. 3, user device 210 may include a housing 305, a microphone 310, aspeaker 315, a keypad 320, and a display 325.

Housing 305 may include a structure to contain components of user device210. For example, housing 305 may be formed from plastic, metal, or someother material. Housing 305 may support microphone 310, speakers 315,keypad 320, and display 325.

Microphone 310 may include an input device that converts a sound wave toa corresponding electrical signal. For example, the user may speak intomicrophone 310 during a telephone call or to execute a voice command.Speaker 315 may include an output device that converts an electricalsignal to a corresponding sound wave. For example, the user may listento music, listen to a calling party, or listen to other auditory signalsthrough speaker 315.

Keypad 320 may include an input device that provides input into userdevice 210. Keypad 320 may include a standard telephone keypad, a QWERTYkeyboard, and/or some other type or arrangement of keys. Keypad 320 mayalso include one or more special purpose keys. The user may utilizekeypad 320 as an input component to user device 210. For example, theuser may use keypad 320 to enter information, such as alphanumeric text,to access data, or to invoke a function or an operation.

Display 325 may include an output device that outputs visual content,and/or may include an input device that receives user input (e.g., atouch screen (also known as a touch display)). Display 325 may beimplemented according to a variety of display technologies, such as, aliquid crystal display (LCD), a plasma display panel (PDP), a fieldemission display (FED), a thin film transistor (TFT) display, or someother type of display technology. Additionally, display 325 may beimplemented according to a variety of sensing technologies, such as,capacitive sensing, surface acoustic wave sensing, resistive sensing,optical sensing, pressure sensing, infrared sensing, gesture sensing,etc. Display 325 may display text, images, and/or video to the user.Display 325 may also display a user interface (e.g., a graphical userinterface (GUI)) of user device 210 or a user interface of some otherdevice which user device 210 controls, a user interface associated withapplications, or the like.

Although FIG. 3 shows example components of user device 210, in otherimplementations, user device 210 may contain fewer components, differentcomponents, differently arranged components, or additional componentsthan depicted in FIG. 3. For example, in some implementations, userdevice 210 may include a camera or another type of optical sensor.Alternatively, or additionally, one or more components of user device210 may perform one or more other tasks described as being performed byone or more other components of user device 210.

FIG. 4 is a diagram of example components of a device 400 according toone or more implementations described herein. In certainimplementations, device 400 may correspond to one or more of the devicesdepicted in FIG. 2. For example, device 400 may correspond to userdevice 210 and/or message security system 230. Additionally, each ofuser device 210 and/or message security system 230 may include one ormore devices 400 or one or more components of device 400.

As depicted, device 400 may include bus 410, processor 420, memory 430,input device 440, output device 450, and communication interface 460.However, in other implementations, device 400 may include fewercomponents, additional components, different components, or differentlyarranged components than those illustrated in FIG. 4.

Bus 410 may include one or more component subsystems and/orcommunication paths that enable communication among the components ofdevice 400. Processor 420 may include one or more processors,microprocessors, data processors, co-processors, network processors,application-specific integrated circuits (ASICs), controllers,programmable logic devices (PLDs), chipsets, field-programmable gatearrays (FPGAs), or other types of components that may interpret orexecute instructions or data. Processor 420 may control the overalloperation, or a portion thereof, of device 400, based on, for example,an operating system, and/or various applications. Processor 420 mayaccess instructions from memory 430, from other components of device400, or from a source external to device 400 (e.g., a network or anotherdevice).

Memory 430 may include memory and/or secondary storage. For example,memory 430 may include random access memory (RAM), dynamic RAM (DRAM),read-only memory (ROM), programmable ROM (PROM), flash memory, or someother type of memory. Memory 430 may include a hard disk (e.g., amagnetic disk, an optical disk, a magneto-optic disk, a solid statedisk, etc.) or some other type of computer-readable medium, along with acorresponding drive. A computer-readable medium may be defined as anon-transitory memory device. A memory device may include space within asingle physical memory device or spread across multiple physical memorydevices.

Input device 440 may include one or more components that permit a userto input information into device 400. For example, input device 440 mayinclude a keypad, a button, a switch, a knob, fingerprint recognitionlogic, retinal scan logic, a web cam, voice recognition logic, atouchpad, an input port, a microphone, a display, or some other type ofinput component. Output device 450 may include one or more componentsthat permit device 400 to output information to a user. For example,output device 450 may include a display, light-emitting diodes (LEDs),an output port, a speaker, or some other type of output component.

Communication interface 460 may include one or more components thatpermit device 400 to communicate with other devices or networks. Forexample, communication interface 460 may include some type of wirelessor wired interface. Communication interface 430 may also include anantenna (or a set of antennas) that permit wireless communication, suchas the transmission and reception of radio frequency (RF) signals.

As described herein, device 400 may perform certain operations inresponse to processor 420 executing software instructions contained in acomputer-readable medium, such as memory 430. The software instructionsmay be read into memory 430 from another computer-readable medium orfrom another device via communication interface 460. The softwareinstructions contained in memory 430 may cause processor 420 to performone or more processes described herein. Alternatively, hardwiredcircuitry may be used in place of, or in combination with, softwareinstructions to implement processes described herein. Thus,implementations described herein are not limited to any specificcombination of hardware circuitry and software.

FIG. 5 is a diagram of example functional components of user device 210according to one or more implementations described herein. Asillustrated, user device 210 may include message management module 510and key management module 520. Depending on the implementation, one ormore of modules 510-520 may be implemented as a combination of hardwareand software based on the components illustrated and described withrespect to FIG. 4. Alternatively, modules 510-520 may each beimplemented as hardware based on the components illustrated anddescribed with respect to FIG. 4.

Message management module 510 may provide functionality with respect toelectronic messages. For example, message management module 510 mayenable user device 210 to create electronic messages, associatepersonalized security keys with electronic messages, encrypt electronicmessages based on personalized security keys, and/or communicateelectronic message to devices of intended recipients. Message managementmodule 510 may also, or alternatively, enable user device 210 to receiveelectronic messages and/or decrypt electronic messages usingpersonalized security keys. Additionally, or alternatively, messagemanagement module 510 may enable user device 210 to perform one or moreother functions or operations, such as prohibiting a personalizedsecurity key from being used to decrypt an electronic message if a keyduration associated with the personalized security key has expired.

Key management module 520 may provide functionality with respect topersonalized security keys. For example, key management module 520 mayenable user device 210 to receive personalized security keys from users,receive key durations from users, and/or associate personalized securitykeys with key durations. Additionally, or alternatively, key managementmodule 520 may enable user device 210 to prompt users to inputpersonalized security key information and/or use personalized securitykey information to obtain personalized security keys. Key managementmodule 520 may enable user device 210 to perform one or more additional,or alternative, functions or operations, such as determine whether a keyduration associated with a personalized security key has expired and, ifso, prohibit the personalized security key to be used to decrypt acorresponding electrical message.

In addition to the functionality described above, functional componentsof user device 210 may also, or alternatively, provide functionality asdescribed elsewhere in this specification. Additionally, oralternatively, as described below, one or more of the functions oroperations of user device 210 may be performed by another device, suchas message security system 230. Further, while FIG. 4 shows a particularnumber and arrangement of modules, in alternative implementations, userdevice 210 may include additional modules, fewer modules, differentmodules, or differently arranged modules than those depicted.

FIG. 6 is a diagram of an example process 600 for creating andcommunicating an electronic message according to one or moreimplementations described herein. In one or more implementations,process 600 may be performed by one or more components of user device210. In other implementations, some or all of process 600 may beperformed by one or more other components/devices, or a group ofcomponents/devices, including or excluding user device 210. For example,message security system 230 may perform some or all of process 600.

An electronic message may be created (block 610). For example, userdevice 210 may create an electronic message. As mentioned above,examples of an electronic message may include an e-mail message, a textmessage, an instant message, a voicemail message, a video-mail message,or another type of electronic message. In some implementations, userdevice 210 may create the electronic message in response to one or moreinputs or commands received from a user of user device 210.

A personalized security key may be received (block 620). For instance,user device 210 may receive a personalized security key from a user. Thepersonalized security key may correspond to one or more security keytypes (e.g., an audio passphrase, a user device gyration pattern, a textpattern, a visual pattern (e.g., facial recognition), etc.). In someimplementations, user device 210 may provide an array, a list, or a menuof security key types, and prompt the user to select one or more of thesecurity key types. This may notify user device 210 to focus on one ormore types of user inputs in order to receive the personalized securitykey. For example, the user may select a user device gyration pattern asthe security key type, and user device 210 may treat a subsequentgyration pattern experienced by user device 210 as the personalizedsecurity key. As such, one or more of the implementations describedherein provide solutions for enabling a user to personalize a securitykey by selecting a particular security key type, and, in turn, furtherpersonalize the security key by enabling the user to enter the actualkey information.

The personalized security key may be associated with the electronicmessage (block 630). For example, user device 210 may associate thepersonalized security key received from the user with the electronicmessage. In some implementations, user device 210 may locally store thepersonalized security key. In other implementations, user device 210 mayalso, or alternatively, communicate the personalized security key tomessage security system 230. In such implementations, as discussed ingreater detail below, a receiving user device 210 (e.g., the user deviceof an intended recipient) may obtain the personalized security keycorresponding to the electronic message by communicating with messagesecurity system 230.

The electronic message may be encrypted with the personalized securitykey (block 640). For instance, user device 210 may operate to encryptthe electronic message using the personalized security key. As discussedbelow, the personalized security key may later be used by a receivinguser device 210 to decrypt the electronic message. As such, theelectronic message may be encrypted by a security key that was derivedfrom a particular input from the user sending the electronic message.

A key duration may be specified for the personalized security key (block650). For example, user device 210 may receive a key duration,corresponding to the personalized security key, from the user. Asmentioned above, the key duration may include an interval of time,specified by the user, during which the personalized security key may beused to decrypt the electronic message. As such, attempts to decrypt theelectronic message prior to, or subsequent to, the interval of timecorresponding to the key duration may be prohibited or otherwiseunsuccessful. As such, one or more of the implementations describedherein may enable a user to further protect the electronic message byimposing time constraints on when the personalized security key may beused to decrypt the electronic message.

The electronic message may be communicated to an intended recipient(block 660). For example, user device 210 may communicate the electronicmessage to an intended recipient (e.g., to the user device of theintended recipient). In some implementations, user device 210 maycommunicate the electronic message to another user device 210 vianetwork 220. In another implementation, user device 210 may communicatethe electronic message to another user device 210 via message securitysystem 230

While FIG. 6 shows a flowchart diagram of an example process 600 forcreating and communicating an electronic message, in otherimplementations, a process for creating and communicating an electronicmessage may include fewer operations, different operations, differentlyarranged operations, or additional operations than depicted in FIG. 6.

FIG. 7 is a diagram of an example process 700 for decrypting anelectronic message according to one or more implementations describedherein. In one or more implementations, process 700 may be performed byone or more components of user device 210. In other implementations,some or all of process 700 may be performed by one or more othercomponents/devices, or a group of components/devices, including orexcluding user device 210. For example, message security system mayperform some or all of process 700

An electronic message may be received (block 710). For example, userdevice 210 may receive an electronic message from another user device210. In some implementations, the electronic message may have beenencrypted using a security key corresponding to one or more user inputs.As mentioned above, examples of such a user input may include a usermoving or gyrating user device 210 in a particular pattern, the userspeaking into a microphone of user device 210, the user typing asequence of characters into a keyboard of user device 210, or the userspecifying optical information (e.g., facial recognition data), etc.

Personalized security key information may be received (block 720). Forinstance, user device 210 may receive personalized security keyinformation from a user. In some implementations, user device 210 mayprompt the user for the personalized security key information. Examplesof personalized security key information may include the same type ofinformation received from the user of the sending user device 210 tocreate the personalized security key used to encrypt the electronicmessage. For instance, if the sending user device 210 used a user devicegyration pattern to create a personalized security key and encrypt theelectronic message, the personalized security key information receivedby the receiving user device 210 may be the same user device gyrationpattern. In other implementations, the personalized security keyinformation may be a set of information that is complementary orotherwise associated with the information received by the sending userdevice 210. For example, if the sending user device 210 used a circularuser device gyration pattern to create the personalized security key andencrypt the electronic message, the personalized security keyinformation received by the receiving user device 210 may be a linearuser device gyration pattern. Information specifying the appropriatetypes of user inputs for encrypting the electronic message andinformation specifying the appropriate types of user inputs fordecrypting the electronic message may be stored by the sending userdevice 210, stored by message security system 230, and/or received bythe receiving use device 210. In other implementations, the personalizedsecurity key information may be one or more types of informationidentifying the user of the receiving user device 210, such as a username, a password, an e-mail address, or another type of informationidentifying the user of the receiving user device 210.

A personalized security key may be obtained (block 730). For example,user device 210 may obtain a personalized security key for decryptingthe electronic message. The personalized security key may be thepersonalized security key used to encrypt the electronic message. Insome implementations, user device 210 may obtain the personalizedsecurity key by generating the personalized security key based on thepersonalized security key information received from the user. In otherimplementations, user device 210 may obtain the personalized securitykey be communicating with the sending user device 210 and/or messagesecurity system 230. For example, the receiving user device 210 maycommunicate the personalized security key information to the sendinguser device 210, and the sending user device 210 may authenticate thereceiving user device 210 (or the user of the receiving user device 210)and communicate the personalized security key to the receiving userdevice 210. Similarly, the receiving user device 210 may communicate thepersonalized security key information to message security system 230,and message security system 230 may authenticate the receiving userdevice 210 (or the user of the receiving user device 210) andcommunicate the personalized security key to the receiving user device210.

A key duration of the personalized security key may be verified (block740). For instance, user device 210 may determine whether a key durationcorresponding to the personalized security key has expired. As mentionedabove with reference to FIG. 6, the sending user device 210 may specifya key duration for a personalized security key. The key duration mayidentify a period of time when the personalized security key may be usedto decrypt the electronic message. As such, the receiving user device210 may verify that the key duration corresponding to a personalizedsecurity key has not expired at some point prior to using thepersonalized security key to decrypt the electronic message. In someimplementations, if the key duration has expired, the receiving userdevice 210 may be prohibited from using the personalized security key todecrypt or otherwise access the electronic message. In someimplementations, the key duration of the personalized security key maybe verified by the sending user device 210 and/or message securitysystem 230, and, if the key duration has expired, the sending userdevice 210 and/or message security system 230 may refuse to send thepersonalized security key to user the receiving user device 210.

The electronic message may be decrypted with the personalized securitykey (block 750). For instance, user device 210 may use the personalizedsecurity key to decrypt the electronic message. As mentioned above, thepersonalized security key may be generated by user device 210 locally,received from the sending user device 210, or received from messagesecurity system 230. In some implementations, however, once the keyduration of the personalized security key has expired, the receiving theelectronic message may not be decrypted or otherwise viewed (even if theelectronic message was previously decrypted by the receiving user device210).

While FIG. 7 shows a flowchart diagram of an example process 700 fordecrypting an electronic message, in other implementations, a processfor decrypting an electronic message may include fewer operations,different operations, differently arranged operations, or additionaloperations than depicted in FIG. 7.

FIG. 8 is a diagram of an example process 800 for communicating anelectronic message according to one or more implementations describedherein. As depicted, sending user device 210 may create an electronicmessage (event 810). Sending user device 210 may also specify apersonalized security key and a key duration for the electronic message(event 820). Sending user device 210 may then encrypt the electronicmessage using the personalized security key (event 830) and communicatethe electronic message to receiving user device 210 (event 840).

Receiving user device 210 may communicate personalized security keyinformation to the sending user device (event 850), and the sending userdevice may authenticate 860 the personalized security key information(event 860). Sending user device 210 may communicate the personalizedsecurity key and the key duration to receiving user device 210 (event870), and receiving user device 210 may verify that the key duration hasnot expired (event 880) and proceed to decrypt the electronic message(event 890). In some implementations, sending user device 210 maydetermine whether the key duration has expired and, if the key durationhas expired, may refuse to provide receiving user device 210 with thepersonalized security key. In some implementations, however, once thekey duration of the personalized security key has expired, the receivingthe electronic message may not be decrypted or otherwise viewed (even ifthe electronic message was previously decrypted by the receiving userdevice 210). In some implementations, if the key duration has expired,in some implementations, user device 210 may prohibit the security keyfrom being used to decrypt the electronic message, delete the securitykey, re-encrypt the electronic message with another security key, deletethe electronic message, or generate a password, associate the passwordwith the electronic message, and require the user to enter the passwordin order to gain access to the content of the electronic message.

While FIG. 8 shows a flowchart diagram of an example process 800 forcommunicating an electronic message, in other implementations, a processfor communicating an electronic message may include fewer operations,different operations, differently arranged operations, or additionaloperations than depicted in FIG. 8.

FIG. 9 is a diagram of another example process 900 for communicating anelectronic message according to one or more implementations describedherein. As depicted, sending user device 210 may create an electronicmessage (event 910). Sending user device 210 may also, or alternatively,specify a personalized security key and key duration corresponding tothe electronic message (event 920). Sending user device 210 maycommunicate the personalized security key and the key duration to securemessage system 230 (event 930). Additionally, or alternatively, sendinguser device 210 may encrypt the electronic message (event 940) andcommunicate the electronic message to receiving user device 210 (event950).

Receiving user device 210 may communicate personalized security keyinformation to secure message system 230 (event 960), and secure messagesystem 230 may authenticate receiving user device 210 based on thepersonalized security key information (event 970). Secure message system230 may also, or alternatively, communicate the personalized securitykey and/or the key duration to receiving user device 210 (event 980).Receiving user device 210 may verify that the key duration has notexpired (event 990) and decrypt the electronic message using thepersonalized security key (event 995). In some implementations, if thekey duration has expired, receiving user device 210 may be prohibitedfrom decrypting the electronic message.

While FIG. 9 shows a flow diagram of an example process 900 forcommunicating an electronic message, in other implementations, a processfor communicating an electronic message may include fewer operations,different operations, differently arranged operations, or additionaloperations than depicted in FIG. 9.

Accordingly, implementations described herein provide solutions forenhancing the security of electronic messages. For instance,implementations described herein may enable users to encrypt electronicmessages using personalized security keys that may correspond to aparticular type of user input (e.g., user device gyrations, audioinputs, visual inputs, optical data, etc.). Additionally, oralternatively, implementations described herein may enable users tospecify the actual contents of the personalized security key (e.g., aparticular gyration pattern, a particular phrase or word, etc.). Inaddition, implementations described herein may enable users to imposetiming constraints on decrypting or viewing the contents of anelectronic message.

It will be apparent that example aspects, as described above, may beimplemented in many different forms of software, firmware, and hardwarein the implementations illustrated in the figures. The actual softwarecode or specialized control hardware used to implement these aspectsshould not be construed as limiting. Thus, the operation and behavior ofthe aspects were described without reference to the specific softwarecode—it being understood that software and control hardware could bedesigned to implement the aspects based on the description herein.

Further, certain implementations may involve a component that performsone or more functions. These components may include hardware, such as anASIC or a FPGA, or a combination of hardware and software.

Even though particular combinations of features are recited in theclaims and/or disclosed in the specification, these combinations are notintended to limit disclosure of the possible implementations. In fact,many of these features may be combined in ways not specifically recitedin the claims and/or disclosed in the specification. Although eachdependent claim listed below may directly depend on only one otherclaim, the disclosure of the implementations includes each dependentclaim in combination with every other claim in the claim set.

No element, act, or instruction used in the present application shouldbe construed as critical or essential to the implementations unlessexplicitly described as such. Also, as used herein, the article “a” isintended to include one or more items. Where only one item is intended,the term “one” or similar language is used. Further, the phrase “basedon” is intended to mean “based, at least in part, on” unless explicitlystated otherwise.

What is claimed is:
 1. A method comprising: creating, by a user device,an electronic message, the electronic message comprising destinationinformation corresponding to an intended recipient of the electronicmessage; receiving, by the user device and from a user, a security keycorresponding to a particular type of user input and corresponding tothe intended recipient of the electronic message; encrypting, by theuser device, the electronic message based on the security key; andcommunicating, by the user device, the electronic message based on thedestination information corresponding to the intended recipient.
 2. Themethod of claim 1, further comprising: in response to communicating theelectronic message to the intended recipient, receiving security keyinformation corresponding to the intended recipient, where the securitykey information comprises authentication information; determiningwhether the authentication information corresponds to the intendedrecipient; when the authentication information corresponds to theintended recipient, communicating the security key to a devicecorresponding to the intended recipient; and when the authenticationinformation does not correspond to the intended recipient, disregardingthe security key information.
 3. The method of claim 2, where: theauthentication information in the security key information correspondsto the security key used to encrypt the electronic message, anddetermining whether the authentication information corresponds to theintended recipient comprises: determining whether the authenticationinformation corresponds to the security key.
 4. The method of claim 1,further comprising: prompting the user to input the security key; andreceiving the security key from the user.
 5. The method of claim 1,further comprising: providing the user with a menu of security keytypes; prompting the user to select a security key type from the menu ofsecurity key types; receiving a selection, from the user, correspondingto a particular security key type; receiving, from the user, securitykey information corresponding to the particular security key type; andgenerating the security key based on the security key informationreceived from the user.
 6. The method of claim 5, where: the securitykey type comprises: audio information, facial recognition information,user device gyration information, or text pattern information, and thesecurity key information comprises: audio information originating fromthe user, facial recognition information corresponding to the user,facial recognition information corresponding to an intended recipient ofthe electronic message, gyration pattern information corresponding to auser manually moving the user device according to a particular gyrationpattern, or password information corresponding to a pattern of textreceived from the user.
 7. The method of claim 1, further comprising:receiving a key duration from the user; associating the key durationwith the security key; and storing the key duration for subsequent use,where the key duration comprises an interval of time, and whereexpiration of the interval of time corresponding to the key durationrenders the security key inoperative for decrypting the electronicmessage.
 8. The method of claim 7, further comprising: in response tocommunicating the electronic message to the intended recipient,receiving a security key request from a device corresponding to theintended recipient; determining whether the key duration, associatedwith the security key, has expired; when the key duration, associatedwith the security key, has not expired, communicating the security keyto the device corresponding to the intended recipient; and when the keyduration, associated with the security key, has expired, disregard thesecurity key request.
 9. A user device, comprising: a memory to storeinstructions; and a processor, connected to the memory, to: receive anelectronic message, where the electronic message is encrypted with asecurity key corresponding to a user of the user device; prompt the userof the user device to input security key information, where the securitykey information comprises authentication information corresponding tothe electronic message; receive the authentication information from theuser of the user device, where the authentication informationcorresponds to the security key used to encrypt the electronic message;use the authentication information to obtain the security key; anddecrypt the electronic message using the security key.
 10. The userdevice of claim 9, where the security key is based on the authenticationinformation received from the user of the user device.
 11. The userdevice of claim 10, where: the electronic message is received fromanother user device, and to obtain the security key, the processor isto: communicate a security key request to the other user device, wherethe security key request comprises the authentication informationreceived from the user, and receive the security key in response tocommunicating the security request to the other user device.
 12. Theuser device of claim 11, where the processor is to: identify a keyduration associated with the electronic message, where the key durationcomprises an interval of time during which the security key is to beused to decrypt the electronic message, determine whether the keyduration has expired, when the key duration has not expired, decrypt theelectronic message using the security key, and when the key duration hasexpired, prohibit content corresponding to the electronic message frombeing displayed to the user of the user device.
 13. The user device ofclaim 12, where, to prohibit content, corresponding to the electronicmessage, from being displayed to the user of the user device, toprocessor is to: prohibit the security key from being used to decryptthe electronic message, delete the security key, re-encrypt theelectronic message with another security key, delete the electronicmessage, or generate a password, associate the password with theelectronic message, and require the user to enter the password in orderto gain access to the content of the electronic message.
 14. One or morenon-transitory computer-readable storage media, comprising: one or moreinstructions that, when executed by a processor, cause the processor to:create an electronic message in response to receiving one or more inputsfrom a user, where the electronic message comprises destinationinformation corresponding to an intended recipient of the electronicmessage; receive, from the user, a security key corresponding to theintended recipient of the electronic message; encrypt the electronicmessage based on the security key; associate a key duration, receivedfrom the user, with the security key, where the key duration comprises atime interval in which the security key may be used to decrypt theelectronic message; and communicate the electronic message based on thedestination information corresponding to the intended recipient.
 15. Thecomputer-readable storage media of claim 14, further comprising one ormore instructions that, when executed by a processor, cause theprocessor to: receive security key information from a devicecorresponding to the intended recipient, where the security keyinformation comprises authentication information; determine whether theauthentication information corresponds to the intended recipient; whenthe authentication information corresponds to the intended recipient,communicate the security key to the device corresponding to the intendedrecipient; and when the authentication information does not correspondto the intended recipient, disregard the security key information. 16.The computer-readable storage media of claim 15, where: theauthentication information corresponding to the security key informationcorresponds to security used to encrypt the electronic message, anddetermining whether the authentication information corresponds to theintended recipient comprises: determining whether the authenticationinformation corresponds to the security key.
 17. The computer-readablestorage media of claim 14, further comprising one or more instructionsthat, when executed by a processor, cause the processor to: prompt theuser to input the security key; and receive the security key from theuser.
 18. The computer-readable storage media of claim 14, furthercomprising one or more instructions that, when executed by a processor,cause the processor to: provide the user with a menu of security keytypes; prompt the user to select a security key type from the menu ofsecurity key types; receive a selection, from the user, corresponding toa particular security key type; receive, from the user, security keyinformation corresponding to the particular security key type from themenu of security key types; and generate the security key based on thesecurity key information received from the user.
 19. Thecomputer-readable storage media of claim 18, where: the security keytype comprises: audio information, facial recognition information, userdevice gyration information, or text pattern information, and thesecurity key information comprises: audio information originating fromthe user, facial recognition information corresponding to the user,facial recognition information corresponding to an intended recipient ofthe electronic message, gyration pattern information corresponding to auser manually moving the user device according to a particular gyrationpattern, or password information corresponding to a pattern of textreceived from the user.
 20. The computer-readable storage media of claim14, where expiration of the interval of time corresponding to the keyduration renders the security key inoperative for decrypting theelectronic message.
 21. The computer-readable storage media of claim 14,further comprising one or more instructions that, when executed by aprocessor, cause the processor to: in response to communicating theelectronic message to the intended recipient, receiving a security keyrequest from a device corresponding to the intended recipient;determining whether the key duration associated with the security keyhas expired; when the key duration associated with the security key hasnot expired, communicate the security key to the device corresponding tothe intended recipient; and when the key duration associated with thesecurity key has expired, disregard the security key request.